# tblAVIFile

szTitle_tx:
1.6.2 External Unparsed Entities & Notations


# tblConfig

sInstructorBio_tx:
Paul has over ten years of programming experience and is proficient in both Visual Basic and SQL Server.  He has consulted the aerospace, real estate, medicine, and hotel industries.  Paul is a designer of Visual Basic courseware for the Application Developers Training Company, and tours for the Visual Basic Master Seminar Series, training in the United States and Canada.  Paul thoroughly covers every Visual Basic topic.


# tblCourse

szCompanyInfo_tx:
2241 Larsen Parkway
Provo, Utah  84606

800 / 748-4838 (U.S. and Canada)
801 / 375-8680 (International)
801 / 373-6872 (Fax)

www.keystonetraining.com

Support: 800-801-0952

szInstructorBio_tx:
David Harding is an internationally recognized speaker on the topics of client/server and Internet application development. As a consultant, he works with eCommerce companies in the creation and deployment of eCommerce solutions. He has designed and created several commercial eCommerce web sites, has written several training courses and holds industry seminars. David has spoken at several Microsoft events around the world.  He is experienced in numerous languages and databases including C/C++, Visual Basic, SQL Server, and Oracle.


# tblErrors

szProblemMsg_tx:
A general error has occured accessing an ODBC database

szResponseMsg_tx:
Contact tech support. Tell them what you were doing in the program.


szProblemMsg_tx:
The application could not open a database file. This can happen if the application or database has not been installed properly, or if a configuration option is not set correctly.

szResponseMsg_tx:
If the application has just been installed, make sure that the installation was done properly. Otherwise,  check the network connection, file access permissions for the current user, and if the database file still exists.


szProblemMsg_tx:
The application could not append data to the database table.

szResponseMsg_tx:
Contact tech support and tell them that you encountered error number 616.


szProblemMsg_tx:
The application attempted to append records to a table in the database. It was unable to do so.

szResponseMsg_tx:
Contact tech support, and tell them you encountered error number 617.


szShortMsg_tx:
Error: Transaction Processing Not Supported

szProblemMsg_tx:
Most databases support " & Chr$(34) & "transaction processing," & Chr$(34) & "but the database you are connected to does not.

szResponseMsg_tx:
Contact tech support. You may need an updated piece of software, or you may be connected to the wrong file.


szProblemMsg_tx:
The application has referred to an object that is not part of the data collection (where the application thinks it should be).


szProblemMsg_tx:
The database does not support the data type that the application tried to store.

szResponseMsg_tx:
Contact tech support. You may need a new piece of software, a new database file, or you may be connected to the wrong file.


szProblemMsg_tx:
The application referred to a record that is past the end of the file.

szResponseMsg_tx:
Contact tech support RIGHT NOW. This error message can be an indication of a damaged database file--a serious problem. Write down what record you were working on, and what anybody else using the system was doing.


szProblemMsg_tx:
A program error has happened--the application tried to update a record in a database that could not be edited.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 627.


szProblemMsg_tx:
The application tried to change the value of a program property that is set to read-only.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 630.


szProblemMsg_tx:
The application has tried to update a record--but has not yet created the record or opened it for editing.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 632.


szShortMsg_tx:
Error: Tried to Append to TableDefs Collection

szProblemMsg_tx:
The application tried to append (add) a record to a table structure--rather than the table itself.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 633.


szProblemMsg_tx:
The application has attempted to use a database value incorrectly.

szResponseMsg_tx:
Contact tech support, and tell them you have encountered error number 634. You may need new program files or an updated database.


szProblemMsg_tx:
The application attempted to set a database property--but the database table is currently in use.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 635. You may need updated program files.


szProblemMsg_tx:
The application attempted to read data from a table (actually a dynaset) that has not been opened.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 638. You may been updated program files.


szProblemMsg_tx:
The application has attempted to write data to the database--and the field size in the database won't support the size of the variable being written.

szResponseMsg_tx:
Check the data value--you may have accidentally entered a number that is too big. If you continue to get an error message, contact tech support and tell them you have encountered error number 639.


szProblemMsg_tx:
The application has tried to read or change a program property--but the property is not there.

szResponseMsg_tx:
Contact tech support--you may need updated program files. Tell them you encountered error number 643.


szProblemMsg_tx:
The application tried to read a portion of a file--but the size of the portion, or where it began, (or both) was incorrect.

szResponseMsg_tx:
Contact tech support RIGHT NOW. This is usually an indication of a problem with a file. Tell them that you have encountered error number 646.


szProblemMsg_tx:
The application requires a file named VBDB300.DLL. The file could not be located on your system.

szResponseMsg_tx:
Check to be sure that VBDB300.DLL is installed in your file PATH, your \WINDOWS\SYSTEM directory, or in the same directory as the application EXE file.


szProblemMsg_tx:
The application has referred to a number, date, or string incorrectly.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 2420


szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 2421


szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 2422


szProblemMsg_tx:
The application contains an error in the program code that has halted the program.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 2431


szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 2432


szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 2433


szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 2434


szProblemMsg_tx:
The application has attempted to access a database--but cannot find a database with that name.

szResponseMsg_tx:
Contact tech support--you will probably need updated program files.


szShortMsg_tx:
Problem: The Database Is Exclusively Locked

szProblemMsg_tx:
The application cannot open the database--it is presently locked by another user or application.

szResponseMsg_tx:
Someone may be editing the database file directly, or there may be a problem in the program code. Check to see if anyone else is using the database (whether with an application or with a database editor). If no one is, contact tech support.


szProblemMsg_tx:
The application was unable to open a database file.

szResponseMsg_tx:
Check to see if someone else is using the database. If no one is, contact tech support and tell them you have encountered error number 3007.


szProblemMsg_tx:
The application has been prevented from opening a database table. Someone else is using it.

szResponseMsg_tx:
Wait a moment or two and try again. Chances are that the table is only locked momentarily.


szProblemMsg_tx:
The application tried to lock a table in the database, and could not.

szResponseMsg_tx:
Someone else is presently using the same table. Wait a moment and try again. If you still get this message, contact tech support.


szProblemMsg_tx:
The application has tried to find a particular database object, and cannot.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3011. You may need an updated database file.


szProblemMsg_tx:
The application has attempted to open a database table, but cannot.

szResponseMsg_tx:
Contact tech support. You may have to adjust entries in your CONFIG.SYS file (not likely) or there is a program flaw. Tell them you encountered error number 3014.


szProblemMsg_tx:
The application tried to use a database index that doesn't exist.

szResponseMsg_tx:
Contact tech support--this is most likely a case of having a program file that is more current that the database file you're using. Tell them you have encountered error number 3015.


szProblemMsg_tx:
The application has tried to copy the contents of a database record, and the record won't fit.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3016. You may need new programs files or an updated database.


szProblemMsg_tx:
The application has tried to define a text field that is longer than 255 characters.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3017.


szProblemMsg_tx:
The application has tried to access a field--but cannot find it.  Either the table has been modified or you have an outdated database file, or an outdated program.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3018.


szProblemMsg_tx:
The application requires a current index.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3019.


szProblemMsg_tx:
The application has encountered an error updating a database table.

szResponseMsg_tx:
Contact tech support. You will probably need to get updated program files.


szProblemMsg_tx:
The application is looking for a record, and has encountered difficulty.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3021.


szProblemMsg_tx:
The application has attempted to write data to a field--but an identical record exists.

szResponseMsg_tx:
Are you entering a duplicate record? Check your work to be sure that you're not trying to add records that already exist. If necessary, contact tech support and tell them you have encountered error number 3022.


szProblemMsg_tx:
The application has attempted to open a database record--but the record is already open.

szResponseMsg_tx:
Contact tech support. Do NOT continue entering records.


szProblemMsg_tx:
The application is looking for a field in the database that is not there.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error 3024. Do not continue entering data.


szProblemMsg_tx:
The application cannot open any more files--as a result, it has stopped.

szResponseMsg_tx:
Contact tech support and tell them you have encountered error 3025. You will probably need to increase the "FILES="  statement in your CONFIG.SYS file, but check with tech support first.


szProblemMsg_tx:
The application cannot write data to the disk drive, because it is full.

szResponseMsg_tx:
Use File Manager to remove unused files from your disk drive. If you do not know which files are safe to remove, check with your LAN administrator or contact tech support.


szProblemMsg_tx:
The application is trying to write data to a read-only database.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3027.


szProblemMsg_tx:
Your application requires the presence of a file named SYSTEM.MDA. The application cannot open it, probably because it cannot find it.

szResponseMsg_tx:
Check to be sure that any network connections are still valid, and that the SYSTEM.MDA file is visible on your system. If the problem reoccurs, contact tech support and tell them you have error number 3028.


szShortMsg_tx:
Error: Not a Valid Account Name or Password

szProblemMsg_tx:
Your application has attempted to attach to the network, but the account name or password was not accepted.

szResponseMsg_tx:
Contact your LAN administrator to be sure that you are using the correct name and password. Then try again.


szProblemMsg_tx:
Your application has attempted to attach to the network, but the account name given is not valid.

szResponseMsg_tx:
Contact your LAN administrator to get the correct name to use.


szProblemMsg_tx:
Your application has attempted to attach to the network, but the password given is not valid.

szResponseMsg_tx:
Try re-entering the password. If it still doesn't work, contact your LAN administrator.


szProblemMsg_tx:
Your application has attempted to delete a network account. It cannot do so.

szResponseMsg_tx:
In all likelihood the account could not be deleted because somebody is presently using it. Contact your LAN administrator.


szProblemMsg_tx:
Your application tried to read or write data from a directory or file to which you do not have appropriate rights.

szResponseMsg_tx:
Contact your LAN administrator for permission to use the file, or contact tech support.


szProblemMsg_tx:
Your application attempted to save a database entry--but never began one.

szResponseMsg_tx:
Contact tech support--do NOT continue data entry.


szProblemMsg_tx:
A memory allocation error has occured. You may need more memory in your system or you will need to close some Windows applications

szResponseMsg_tx:
Please close some Windows applications. If this error occurs again, contact tech support.


szShortMsg_tx:
Error: Database Has Reached Maximum Size

szProblemMsg_tx:
One of your database files has reached the maximum possible size for that type of file. You cannot add any more information to the file.

szResponseMsg_tx:
Depending on the database format, you may be able to compact the file to gain more space. You should, however, contact tech support.


szShortMsg_tx:
Error: Can't Open Any More Tables or Queries

szProblemMsg_tx:
Your application has tried to open more tables or queries than is permitted.

szResponseMsg_tx:
Contact tech support, and tell them you have encountered error number 3037. Do NOT continue data entry.


szProblemMsg_tx:
An error was encountered while attempting to access your hard disk drive.

szResponseMsg_tx:
Contact tech support immediately. Do NOT continue data entry. Tell them you have encountered error number 3040.


szProblemMsg_tx:
Your application cannot open a database file--the file is the wrong version.

szResponseMsg_tx:
Check your startup information--the application may be opening the wrong file. Check to be sure that your data files are correctly installed. If this error persists, contact tech support.


szProblemMsg_tx:
Your computer system needs to have a change made to your CONFIG.SYS file.

szResponseMsg_tx:
Change the "FILES=" line in your CONFIG.SYS file to 40 or more. If you have never edited CONFIG.SYS, contact your LAN administrator or call tech support.


szProblemMsg_tx:
Your application has attempted to access files on your hard drive, or on the network, and could not.

szResponseMsg_tx:
If you are using a Local Area Network, attempt to re-connect to the LAN. Contact your LAN Adminstrator for help and more instructions.


szProblemMsg_tx:
You attempted to store something on a path that does not exist

szResponseMsg_tx:
Contact tech support and tell them what you were doing.


szProblemMsg_tx:
Your application cannot open a file--another user or application is using it.

szResponseMsg_tx:
Contact tech support and tell them you have encountered error number 3045.


szProblemMsg_tx:
Your application is trying to read or write information--but another user has that part of the database locked.

szResponseMsg_tx:
Try continuing--the problem may not happen again. If this error continues, contact tech support and tell them you have encountered error number 3046


szShortMsg_tx:
Error: Some database or table has become corrupted.

szProblemMsg_tx:
A database or table has become corrupted or is not compatible with Visual Basic.


szProblemMsg_tx:
You have not loaded SHARE.EXE in your Autoexec.bat file. Please put the following line in your autoexec.bat.

SHARE /L:500

szResponseMsg_tx:
You will need to exit windows, and reboot your machine. Then try the application again. If you continue to receive this message contact tech support


szProblemMsg_tx:
Your application tried to open a file, and could not.

szResponseMsg_tx:
Contact tech support--tell them you have encountered error number 3051. Do NOT continue data entry.


szProblemMsg_tx:
Your computer system doesn't have the SHARE lock count set high enough.

szResponseMsg_tx:
Change the SHARE line in your AUTOEXEC.BAT file. It should be set to 500 locks or higher.


szShortMsg_tx:
Error: Too Many Memo or Long Binary Fields

szProblemMsg_tx:
Your database file format does not support all the fields defined by your application.

szResponseMsg_tx:
Contact tech support. Tell them you have encountered error number 3054. They will need to revise the application or change your database file format.


szProblemMsg_tx:
You have entered a file name that the operating system does not recognize.

szResponseMsg_tx:
Please reenter the file name. Refer to your DOS manual for more help on valid file names.


szProblemMsg_tx:
The application attempted to repair the database, and could not.

szResponseMsg_tx:
Contact tech support--stop ALL data entry immediately!


szShortMsg_tx:
Error: Operation not allowed on attached tables

szProblemMsg_tx:
An operation has been attempted from your application to a table that is remote.


szProblemMsg_tx:
The application has tried to save a value that has not been entered.

szResponseMsg_tx:
Check to be sure that you have all the fields filled in. Contact tech support, and tell them you have encountered error number 3058.


szProblemMsg_tx:
You cancelled an operation that was in progress.

szResponseMsg_tx:
Cancelling the action may have undesireable results. Contact tech support, and tell them what happened. Do not continue data entry until you have talked with them.


szProblemMsg_tx:
The application could not correctly express the search you described.

szResponseMsg_tx:
Try the search again. If you still need help, check the program documentation, and contact tech support.


szProblemMsg_tx:
The application is missing a data table.

szResponseMsg_tx:
Contact tech support. Tell them what you were doing in the program, and ask for an updated program file.


szProblemMsg_tx:
A data buffer has overflowed when accessing a table through ODBC


szShortMsg_tx:
Error: ODBC detected an incorrect DLL file

szProblemMsg_tx:
A DLL file is either out of date, or is the wrong one for the ODBC driver.

szResponseMsg_tx:
Contact tech support. Tell them what you were doing in the program. You may need an updated driver.


szResponseMsg_tx:
Contact tech support and request a new DLL for ODBC.


szShortMsg_tx:
Error: Connection to this ODBC item has failed

szProblemMsg_tx:
ODBC tried to connect to an object and has failed


szProblemMsg_tx:
Your machine has an outdated set of ODBC drivers

szResponseMsg_tx:
Contact tech support and request the latest ODBC drivers.


szShortMsg_tx:
Error: Incorrect ODBC version for Server

szProblemMsg_tx:
Your server has an outdated set of ODBC drivers that are incompatible with the ones on your machine.

szResponseMsg_tx:
Contact tech support for the latest ODBC drivers.


szShortMsg_tx:
Error: ODBC can't locate a DLL file it needs

szProblemMsg_tx:
ODBC can't find a DLL file it needs to establish a connection.


szProblemMsg_tx:
An attempt to add a new item to an ODBC table or database has failed


szProblemMsg_tx:
An attempt to delete an item from an ODBC table or database has failed


szProblemMsg_tx:
An attempt to update an item in an ODBC table or database has failed


szResponseMsg_tx:
Try continuing--the problem may not happen again. If this error continues, contact tech support and tell them you have encountered error number 3158


szProblemMsg_tx:
The application has tried to access a data table that has not been opened.

szResponseMsg_tx:
Contact tech support--tell them you have encountered error number 3160.


szProblemMsg_tx:
Your application stores data in encrypted form--the application could not decrypt the data it needs.

szResponseMsg_tx:
Check to be sure that you have the correct version of the database file installed. If you do, contact tech support immediately.


szShortMsg_tx:
Error: Could not insert or paste; data too long for field.

szProblemMsg_tx:
You entered too much data in a field on the screen.

szResponseMsg_tx:
Contact tech support and tell them the screen you were on. Then cut down the amount of text in some of your fields.


szProblemMsg_tx:
This field could not be updated on the table.

szResponseMsg_tx:
Contact tech support and tell them which screen you were on.


szProblemMsg_tx:
Your application attempted to access a database record, but the record has already been deleted.

szResponseMsg_tx:
If possible, use another means to determine that the record is not there. If it is (so this message is mistaken) contact tech support.


szShortMsg_tx:
Error: Couldn't find installable ISAM driver.

szProblemMsg_tx:
The program needs an ISAM driver to run this application or open a particular database.

szResponseMsg_tx:
Contact tech support for the latest drivers to run the program.


szShortMsg_tx:
Error: Couldn't find net path or user name.

szProblemMsg_tx:
A request for a specific path on the network, or user name on the network is invalid.

szResponseMsg_tx:
Contact tech support and tell them what you were doing in the program.


szProblemMsg_tx:
The file PARADOX.NET must be installed on your system.

szResponseMsg_tx:
Contact tech support and ask them where you can obtain this file.


szShortMsg_tx:
Error: Couldn't open table MSysAccounts in the system database.

szProblemMsg_tx:
The program could not open the table MSysAccounts.


szShortMsg_tx:
Error: Couldn't open table MSysGroups in the system database.

szProblemMsg_tx:
The program could not open the table MSysGroups.


szProblemMsg_tx:
The program was unable to open the file name specified.


szShortMsg_tx:
Error: Not Enough Space on Temporary Disk

szProblemMsg_tx:
The program needs to use your temporary disk--but there is not enough space free.

szResponseMsg_tx:
Check to see if you have other programs using the temporary disk (such as print caching software). Remove those programs, or check with tech support.


szResponseMsg_tx:
Try continuing--the problem may not happen again. If this error continues, contact tech support and tell them you have encountered error number 3186


szProblemMsg_tx:
The record you need (or one nearby in the database) is currently locked.

szResponseMsg_tx:
Try repeating the action once or twice. If the problem persists, contact tech support.


szProblemMsg_tx:
The data record you are trying to change has been changed since you read it.

szResponseMsg_tx:
Contact tech support--do not continue, or you will overwrite data that has been saved by another user.


szProblemMsg_tx:
The program uses a database that limits the number of sessions available. All sessions are in use.

szResponseMsg_tx:
Check with your LAN administrator or tech support. All check with your co-workers--somebody may have a record open that could be closed.


szProblemMsg_tx:
Can't delete or change record--referential integrity violation


szProblemMsg_tx:
Your application has tried to add data to a detail table--but hasn't added a record header first.


szResponseMsg_tx:
Try continuing--the problem may not happen again. If this error continues, contact tech support and tell them you have encountered error number 3202


szShortMsg_tx:
Error: Operation not supported on Paradox table.

szProblemMsg_tx:
An operation was attempted on a Paradox table with no primary key.


szShortMsg_tx:
Error: Invalid "Deleted" entry in [dBASE ISAM] section in .INI file.

szProblemMsg_tx:
The value in the 'Deleted' section in your .INI file is invalid. Look in the section called [dBASE ISAM].

szResponseMsg_tx:
Contact tech support and inform them what the value is in the .INI file


szShortMsg_tx:
Error: Invalid "Stats" entry in [dBASE ISAM] section in .INI file.

szProblemMsg_tx:
The value in the 'Stats' section in your .INI file is invalid. Look in the section called [dBASE ISAM].


szProblemMsg_tx:
The connect string to your server is too long.


szProblemMsg_tx:
Your application needs to lock a table in the database--but someone else is using it.

szResponseMsg_tx:
Wait a second or two, and try again. If the problem persists, check with your co-workers to see if somebody has a record from the table in use--but might close it.


szShortMsg_tx:
Error: Invalid "Date" entry in [dBASE ISAM] section in .INI file.

szProblemMsg_tx:
The value in the 'Date' section in your .INI file is invalid. Look in the section called [dBASE ISAM].


szShortMsg_tx:
Error: Invalid "Mark" entry in [dBASE ISAM] section in .INI file.

szProblemMsg_tx:
The value in the 'Mark' section in your .INI file is invalid. Look in the section called [dBASE ISAM].


szResponseMsg_tx:
Try continuing--the problem may not happen again. If this error continues, contact tech support and tell them you have encountered error number 3218


szShortMsg_tx:
Error: Invalid entries in [Btrieve ISAM] section in WIN.INI file.

szProblemMsg_tx:
There are one or more errors in the [Btrieve ISAM] section in your WIN.INI file.

szResponseMsg_tx:
Contact tech support and ask for the correct values.


szProblemMsg_tx:
Your database has a damaged data dictionary.

szResponseMsg_tx:
Stop what you are doing. Write down what you are presently doing, and what the other people in your workgroup are doing. Call tech support immediately.


szProblemMsg_tx:
You have a record open that another user needs--and that user has a record open that you need.

szResponseMsg_tx:
Both of you are pretty well stuck. Write down what you're doing, and contact tech support.


szProblemMsg_tx:
The application couldn't find the right Btrieve database DLL file.

szResponseMsg_tx:
Chances are you have recently installed another application that has installed a new DLL file. Check with tech support to see if you need an updated program file.


szShortMsg_tx:
Error: Invalid "Century" entry in [dBASE ISAM] section in .INI file.

szProblemMsg_tx:
The value in the 'Century' section in your .INI file is invalid. Look in the section called [dBASE ISAM].


szShortMsg_tx:
Error: Invalid "CollatingSequence" entry in [Paradox ISAM] section in .INI file.

szProblemMsg_tx:
The value in the 'CollatingSequence' section in your .INI file is invalid. Look in the section called [Paradox ISAM].


szProblemMsg_tx:
The Paradox lock file being utilized is out of date from the table.

szResponseMsg_tx:
Contact tech support and ask for instructions on how to update your system.


szProblemMsg_tx:
Your application has encountered an error working with an ODBC database.

szResponseMsg_tx:
Check your network connections, particularly connections to your database server. If they're OK, check with your LAN administrator or with tech support.


szProblemMsg_tx:
Your application (probably the database) limits the number of users who can be logged on at a time. You're over the limit.

szResponseMsg_tx:
Check with your LAN adminstrator--and with your co-workers. There may be somebody who's still logged in that doesn't need to be.


szProblemMsg_tx:
The application couldn't find the right Btrieve database DLL file. (WBTRCALL.DLL)


szShortMsg_tx:
Error: Invalid "NetworkAccess" in .INI File

szProblemMsg_tx:
The entry in the "NetworkAccess" section of your .INI file is in error

szResponseMsg_tx:
Contact tech support and ask them for the correct entry.


szShortMsg_tx:
Error: Invalid "PageTimeout" in .INI File

szProblemMsg_tx:
The entry in the "PageTimeout" section of your .INI file is in error


szProblemMsg_tx:
ODBC cannot lock all records on the database it is connected to.

szResponseMsg_tx:
Contact tech support and ask them for new drivers, or an updated application.


szResponseMsg_tx:
Contact tech support and ask for an updated program.


szResponseMsg_tx:
Try continuing--the problem may not happen again. If this error continues, contact tech support and tell them you have encountered error number 3260


szProblemMsg_tx:
Your application tried to access a database feature that your database doesn't support.


szProblemMsg_tx:
Your application tried to change a value (probably in the database) that isn't the right type for the change that was attempted.


szProblemMsg_tx:
Your system has an out of date or incorrect version of ODBC

szResponseMsg_tx:
Contact tech support and ask them for the latest ODBC drivers.


szShortMsg_tx:
Error: Invalid operation for an Access 1.1 database.

szProblemMsg_tx:
An operation has been attempted that is invalid in the Access 1.1 database.

szResponseMsg_tx:
Contact tech support and ask them for the latest copy of the application.


# tblKeyword

szKeyword_tx:
Viewing the Reference to the Entity Name


szKeyword_tx:
Viewing Parameter Entities and Conditional Markup


szKeyword_tx:
Creating a Reusable Set of Parameter Entities


szKeyword_tx:
Including the Entity Contents in a Document


szKeyword_tx:
Processing of Binary (and Other Non-Parsed) Entities


szKeyword_tx:
Example of Using an External Binary Entity


szKeyword_tx:
A Few Final Words on DTD's and Modularity


# tblSections

sSection_nm:
1.6 External Unparsed Entities & Notations


# tblTextFile

szTitle_tx:
TU 21 Specifying a Path to Lesson Folders


szTitle_tx:
1.6 External Unparsed Entities & Notations


# tblSCFile

szTitle_tx:
1.6.1 External Unparsed Entities & Notations


